System and method for establishing permanent records based on microinteractions

ABSTRACT

Embodiments of the present invention provide a system for establishing permanent records based on micro-interactions. In particular, the system may be configured to identify initiation of an event based on receiving first set of interaction requests from user devices of one or more users, initiate a first set of micro-interactions, wherein initiation of the first set of micro-interactions comprises transferring resources to one or more resource pools associated with the one or more users, identify completion of the event based on receiving a second set of interaction requests from the user devices of the one or more users, revert the first set of micro-interactions, wherein reverting the first set of micro-interactions comprises transferring the resources back from the one or more resource pools associated with the one or more users, and create a permanent record associated with the initiation of the event and the completion of the event.

BACKGROUND

Typically, conventional systems do not have the ability to verify usersof a future interaction and also establish records associated withinteractions between the users. As such, there exists a need for asystem to establish permanent records based on micro-interactions.

BRIEF SUMMARY

The following presents a summary of certain embodiments of theinvention. This summary is not intended to identify key or criticalelements of all embodiments nor delineate the scope of any or allembodiments. Its sole purpose is to present certain concepts andelements of one or more embodiments in a summary form as a prelude tothe more detailed description that follows.

Embodiments of the present invention address the above needs and/orachieve other advantages by providing apparatuses (e.g., a system,computer program product and/or other devices) and methods forestablishing permanent records based on micro-interactions. The systemembodiments may comprise one or more memory devices having computerreadable program code stored thereon, a communication device, and one ormore processing devices operatively coupled to the one or more memorydevices, wherein the one or more processing devices are configured toexecute the computer readable program code to carry out the invention.In computer program product embodiments of the invention, the computerprogram product comprises at least one non-transitory computer readablemedium comprising computer readable instructions for carrying out theinvention. Computer implemented method embodiments of the invention maycomprise providing a computing system comprising a computer processingdevice and a non-transitory computer readable medium, where the computerreadable medium comprises configured computer program instruction code,such that when said instruction code is operated by said computerprocessing device, said computer processing device performs certainoperations to carry out the invention.

In some embodiments, the present invention identifies initiation of anevent based on receiving first set of interaction requests from one ormore user devices of one or more users, in response to receiving thefirst set interaction requests, initiates a first set ofmicro-interactions, wherein initiation of the first set ofmicro-interactions comprises transferring resources to one or moreresource pools associated with the one or more users, identifiescompletion of the event based on receiving a second set of interactionrequests from the one or more user devices of the one or more users, inresponse to receiving the second set of interaction requests, revertsthe first set of micro-interactions, wherein reverting the first set ofmicro-interactions comprises transferring the resources back from theone or more resource pools associated with the one or more users, andcreates a permanent record associated with the initiation of the eventand the completion of the event.

In some embodiments, the present invention receives the first set ofinteraction requests and the second set of interaction requests from theone or more users, via an entity device comprising a Near FieldCommunication interface, wherein the first set of interaction requestsand the second set of interaction requests are Near Field Communicationinteraction requests.

In some embodiments, the present invention determines a first set oftime-stamps associated with the first set of the interaction requestsand inserts the first set of time-stamps in the permanent record,wherein the first set of time-stamps are associated with initiation ofthe event.

In some embodiments, the present invention determines a second set oftime-stamps associated with the second set of the interaction requestsand inserts the second set of time-stamps in the permanent record,wherein the second set of time-stamps are associated with completion ofthe event.

In some embodiments, the present invention identifies completion of theevent based on receiving a last interaction request of the second set ofinteraction request, identifies a last time-stamp associated with thelast interaction request, and inserts the last time-stamp as eventcompletion time-stamp in the permanent record.

In some embodiments, the present invention stores the permanent recordon a distributed ledger.

In some embodiments, the present invention transfers the resources andrevert the resources, via an entity application provided by an entity.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 provides a block diagram illustrating a system environment forestablishing permanent records based on micro-interactions, inaccordance with an embodiment of the invention;

FIG. 2 provides a block diagram illustrating the entity system 200 ofFIG. 1 , in accordance with an embodiment of the invention;

FIG. 3 provides a block diagram illustrating an electronic resourcerequest processing system 300 of FIG. 1 , in accordance with anembodiment of the invention;

FIG. 4 provides a block diagram illustrating the computing device system400 of FIG. 1 , in accordance with an embodiment of the invention; and

FIG. 5 provides a block diagram illustrating a process flow forestablishing permanent records based on micro-interactions, inaccordance with an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Where possible, any terms expressed in the singularform herein are meant to also include the plural form and vice versa,unless explicitly stated otherwise. Also, as used herein, the term “a”and/or “an” shall mean “one or more,” even though the phrase “one ormore” is also used herein. Furthermore, when it is said herein thatsomething is “based on” something else, it may be based on one or moreother things as well. In other words, unless expressly indicatedotherwise, as used herein “based on” means “based at least in part on”or “based at least partially on.” Like numbers refer to like elementsthroughout.

As used herein, the term “resource entity” or “entity” may be anyinstitution which involves in financial transactions. In one embodiment,the term “entity” or “resource entity” may be any financial institution.As used herein, the term “entity device” may be any device associatedwith the entity. In some embodiments of the present invention, theentity device may be any device with a Near Field Communication (NFC)interface.

As described herein, a “user” may be a customer or a potential customerof the entity. In some embodiments, a “user” may be a financialinstitution customer (e.g., an account holder or a person who has anaccount (e.g., banking account, credit account, or the like)). An“account” or “resource pool” may be the relationship that the customerhas with the financial institution. Examples of accounts include adeposit account, such as a transactional account (e.g. a bankingaccount), a savings account, an investment account, a money marketaccount, a time deposit, a demand deposit, a pre-paid account, a creditaccount, a non-monetary customer information that includes only personalinformation associated with the customer, or the like. The account isassociated with and/or maintained by a financial institution.

A “user interface” is any device or software that allows a user to inputinformation, such as commands or data, into a device, or that allows thedevice to output information to the user. For example, the userinterface includes a graphical user interface (GUI) or an interface toinput computer-executable instructions that direct a processing deviceto carry out specific functions. The user interface typically employscertain input and output devices to input data received from a user orto output data to a user. These input and output devices may include adisplay, mouse, keyboard, button, touchpad, touch screen, microphone,speaker, LED, light, joystick, switch, buzzer, bell, and/or other userinput/output device for communicating with one or more users.

Conventional systems do not have the capability to create recordsassociated with in-person events and capture additional detailsassociated with in-person events. As such, there exists a need for asystem that creates records associated with in-person events, where therecords comprise all details associated with the in-person events. Thesystem of the present invention establishes a permanent recordassociated with the in-person events based on performingmicro-interactions.

FIG. 1 provides a block diagram illustrating a system environment 100for establishing permanent records based on micro-interactions, inaccordance with an embodiment of the invention. As illustrated in FIG. 1, the environment 100 includes an electronic resource request processingsystem 300, entity system 200, one or more entity devices 201, and acomputing device system 400. One or more users 110 may be included inthe system environment 100, where the users 110 interact with the otherentities of the system environment 100 via a user interface of thecomputing device system 400. In some embodiments, the one or moreuser(s) 110 of the system environment 100 may be customers of an entityassociated with the entity system 200.

The entity system(s) 200 may be any system owned or otherwise controlledby an entity to support or perform one or more process steps describedherein. In some embodiments, the entity is a financial institution. Insome embodiments, the one or more entity devices 201 may be owned,operated, controlled, and/or maintained by the entity. The one or moreentity devices 201 may be any devices that comprise NFC interface.

The electronic resource request processing system 300 is a system of thepresent invention for performing one or more process steps describedherein. In some embodiments, the electronic resource request processingsystem 300 may be an independent system. In some embodiments, theelectronic resource request processing system 300 may be a part of theentity system 200.

The electronic resource request processing system 300, the entity system200, and the computing device system 400 may be in network communicationacross the system environment 100 through the network 150. The network150 may include a local area network (LAN), a wide area network (WAN),and/or a global area network (GAN). The network 150 may provide forwireline, wireless, or a combination of wireline and wirelesscommunication between devices in the network. In one embodiment, thenetwork 150 includes the Internet. In general, the electronic resourcerequest processing system 300 is configured to communicate informationor instructions with the entity system 200, and/or the computing devicesystem 400 across the network 150.

The computing device system 400 may be a system owned or controlled bythe entity of the entity system 200 and/or the user 110. As such, thecomputing device system 400 may be a computing device of the user 110.In general, the computing device system 400 communicates with the user110 via a user interface of the computing device system 400, and in turnis configured to communicate information or instructions with theelectronic resource request processing system 300, and/or entity system200 across the network 150.

FIG. 2 provides a block diagram illustrating the entity system 200, ingreater detail, in accordance with embodiments of the invention. Asillustrated in FIG. 2 , in one embodiment of the invention, the entitysystem 200 includes one or more processing devices 220 operativelycoupled to a network communication interface 210 and a memory device230. In certain embodiments, the entity system 200 is operated by afirst entity, such as a financial institution, while in otherembodiments, the entity system 200 is operated by an entity other than afinancial institution.

It should be understood that the memory device 230 may include one ormore databases or other data structures/repositories. The memory device230 also includes computer-executable program code that instructs theprocessing device 220 to operate the network communication interface 210to perform certain communication functions of the entity system 200described herein. For example, in one embodiment of the entity system200, the memory device 230 includes, but is not limited to, an real-timeresource capacity determination application 250, one or more entityapplications 270, and a data repository 280 comprising user data 283 andentity device data 285, where the user data 283 comprises dataassociated with users 110 and/or one or more resource pools associatedwith the users 110 and the entity device data 285 comprises dataassociated with one or more entity devices. The one or more entityapplications 270 may be any applications provided by the entity thatallows users 110 to access information and/or perform one or moreactions associated with one or more resource pools of the users 110. Thecomputer-executable program code of the network server application 240,the real-time resource capacity determination application 250, the oneor more entity application 270 to perform certain logic,data-extraction, and data-storing functions of the entity system 200described herein, as well as communication functions of the entitysystem 200.

The network server application 240, the real-time resource capacitydetermination application 250, and the one or more entity applications270 are configured to store data in the data repository 280 or to usethe data stored in the data repository 280 when communicating throughthe network communication interface 210 with the electronic resourcerequest processing system 300, and/or the computing device system 400 toperform one or more process steps described herein. In some embodiments,the entity system 200 may receive instructions from the electronicresource request processing system 300 via the real-time resourcecapacity determination application 250 to perform certain operations.The real-time resource capacity determination application 250 may beprovided by the electronic resource request processing system 300.

FIG. 3 provides a block diagram illustrating the electronic resourcerequest processing system 300 in greater detail, in accordance withembodiments of the invention. As illustrated in FIG. 3 , in oneembodiment of the invention, the electronic resource request processingsystem 300 includes one or more processing devices 320 operativelycoupled to a network communication interface 310 and a memory device330. In certain embodiments, the electronic resource request processingsystem 300 is operated by a first entity, such as a financialinstitution, while in other embodiments, the electronic resource requestprocessing system 300 is operated by an entity other than a financialinstitution. In some embodiments, the electronic resource requestprocessing system 300 is owned or operated by the entity of the entitysystem 200. In some embodiments, the electronic resource requestprocessing system 300 may be an independent system. In alternateembodiments, the electronic resource request processing system 300 maybe a part of the entity system 200.

It should be understood that the memory device 330 may include one ormore databases or other data structures/repositories. The memory device330 also includes computer-executable program code that instructs theprocessing device 320 to operate the network communication interface 310to perform certain communication functions of the electronic resourcerequest processing system 300 described herein. For example, in oneembodiment of the electronic resource request processing system 300, thememory device 330 includes, but is not limited to, a networkprovisioning application 340, a real-time data extraction application350, a predictive analysis application 360, an artificial intelligenceapplication 370, a resource capacity determination application 380, anda centralized data repository 390 comprising data processed or accessedby one or more applications in the memory device 330. Thecomputer-executable program code of the network provisioning application340, the real-time data extraction application 350, the predictiveanalysis application 360, the artificial intelligence application 370,and the resource capacity determination application 380 may instruct theprocessing device 320 to perform certain logic, data-processing, anddata-storing functions of the electronic resource request processingsystem 300 described herein, as well as communication functions of theelectronic resource request processing system 300.

The network provisioning application 340, the real-time data extractionapplication 350, the predictive analysis application 360, the artificialintelligence application 370, and the resource capacity determinationapplication 380 are configured to invoke or use the data in the datarepository 390 when communicating through the network communicationinterface 310 with the entity system 200, and/or the computing devicesystem 400. In some embodiments, the network provisioning application340, the real-time data extraction application 350, the predictiveanalysis application 360, the artificial intelligence application 370,and the resource capacity determination application 380 may store thedata extracted or received from the entity system 200, and the computingdevice system 400 in the centralized data repository 390. In someembodiments, the network provisioning application 340, the real-timedata extraction application 350, the predictive analysis application360, the artificial intelligence application 370, and the resourcecapacity determination application 380 may be a part of a singleapplication. The functionalities of the network provisioning application340, the real-time data extraction application 350, the predictiveanalysis application 360, the artificial intelligence application 370,and the resource capacity determination application 380 are explained ingreater detail in FIG. 5 .

FIG. 4 provides a block diagram illustrating a computing device system400 of FIG. 1 in more detail, in accordance with embodiments of theinvention. However, it should be understood that a mobile telephone ismerely illustrative of one type of computing device system 400 that maybenefit from, employ, or otherwise be involved with embodiments of thepresent invention and, therefore, should not be taken to limit the scopeof embodiments of the present invention. Other types of computingdevices may include portable digital assistants (PDAs), pagers, mobiletelevisions, gaming devices, desktop computers, workstations, laptopcomputers, cameras, video recorders, audio/video player, radio, GPSdevices, wearable devices, Internet-of-things devices, augmented realitydevices, virtual reality devices, automated teller machine devices,electronic kiosk devices, or any combination of the aforementioned.

Some embodiments of the computing device system 400 include a processor410 communicably coupled to such devices as a memory 420, user outputdevices 436, user input devices 440, a network interface 460, a powersource 415, a clock or other timer 450, a camera 480, and a positioningsystem device 475. The processor 410, and other processors describedherein, generally include circuitry for implementing communicationand/or logic functions of the computing device system 400. For example,the processor 410 may include a digital signal processor device, amicroprocessor device, and various analog to digital converters, digitalto analog converters, and/or other support circuits. Control and signalprocessing functions of the computing device system 400 are allocatedbetween these devices according to their respective capabilities. Theprocessor 410 thus may also include the functionality to encode andinterleave messages and data prior to modulation and transmission. Theprocessor 410 can additionally include an internal data modem. Further,the processor 410 may include functionality to operate one or moresoftware programs, which may be stored in the memory 420. For example,the processor 410 may be capable of operating a connectivity program,such as a web browser application 422. The web browser application 422may then allow the computing device system 400 to transmit and receiveweb content, such as, for example, location-based content and/or otherweb page content, according to a Wireless Application Protocol (WAP),Hypertext Transfer Protocol (HTTP), and/or the like.

The processor 410 is configured to use the network interface 460 tocommunicate with one or more other devices on the network 150. In thisregard, the network interface 460 includes an antenna 476 operativelycoupled to a transmitter 474 and a receiver 472 (together a“transceiver”). The processor 410 is configured to provide signals toand receive signals from the transmitter 474 and receiver 472,respectively. The signals may include signaling information inaccordance with the air interface standard of the applicable cellularsystem of the wireless network 152. In this regard, the computing devicesystem 400 may be configured to operate with one or more air interfacestandards, communication protocols, modulation types, and access types.By way of illustration, the computing device system 400 may beconfigured to operate in accordance with any of a number of first,second, third, and/or fourth-generation communication protocols and/orthe like.

As described above, the computing device system 400 has a user interfacethat is, like other user interfaces described herein, made up of useroutput devices 436 and/or user input devices 440. The user outputdevices 436 include a display 430 (e.g., a liquid crystal display or thelike) and a speaker 432 or other audio device, which are operativelycoupled to the processor 410.

The user input devices 440, which allow the computing device system 400to receive data from a user such as the user 110, may include any of anumber of devices allowing the computing device system 400 to receivedata from the user 110, such as a keypad, keyboard, touch-screen,touchpad, microphone, mouse, joystick, other pointer device, button,soft key, and/or other input device(s). The user interface may alsoinclude a camera 480, such as a digital camera.

The computing device system 400 may also include a positioning systemdevice 475 that is configured to be used by a positioning system todetermine a location of the computing device system 400. For example,the positioning system device 475 may include a GPS transceiver. In someembodiments, the positioning system device 475 is at least partiallymade up of the antenna 476, transmitter 474, and receiver 472 describedabove. For example, in one embodiment, triangulation of cellular signalsmay be used to identify the approximate or exact geographical locationof the computing device system 400. In other embodiments, thepositioning system device 475 includes a proximity sensor ortransmitter, such as an RFID tag, that can sense or be sensed by devicesknown to be located proximate a merchant or other location to determinethat the computing device system 400 is located proximate these knowndevices.

The computing device system 400 further includes a power source 415,such as a battery, for powering various circuits and other devices thatare used to operate the computing device system 400. Embodiments of thecomputing device system 400 may also include a clock or other timer 450configured to determine and, in some cases, communicate actual orrelative time to the processor 410 or one or more other devices.

The computing device system 400 also includes a memory 420 operativelycoupled to the processor 410. As used herein, memory includes anycomputer readable medium (as defined herein below) configured to storedata, code, or other information. The memory 420 may include volatilememory, such as volatile Random Access Memory (RAM) including a cachearea for the temporary storage of data. The memory 420 may also includenon-volatile memory, which can be embedded and/or may be removable. Thenon-volatile memory can additionally or alternatively include anelectrically erasable programmable read-only memory (EEPROM), flashmemory or the like.

The memory 420 can store any of a number of applications which comprisecomputer-executable instructions/code executed by the processor 410 toimplement the functions of the computing device system 400 and/or one ormore of the process/method steps described herein. For example, thememory 420 may include such applications as a conventional web browserapplication 422, a real-time resource capacity determination application421, entity application 424, an SMS application 423, or the like. Insome embodiments, the entity application 424 may be an online bankingapplication. The real-time resource capacity determination application421 may comprise instructions to a graphical user interface (GUI) on thedisplay 430 that allows the user 110 to interact with the entity system200, the electronic resource request processing system 300, and/or otherdevices or systems. The memory 420 of the computing device system 400may comprise a Short Message Service (SMS) application 423 configured tosend, receive, and store data, information, communications, alerts, andthe like via the wireless telephone network 152. In some embodiments,the real-time resource capacity determination application 421 providedby the electronic resource request processing system 300 allows the user110 to access the electronic resource request processing system 300. Insome embodiments, the entity application 424 provided by the entitysystem 200 and the real-time resource capacity determination application421 allow the user 110 to access the functionalities provided by theelectronic resource request processing system 300 and the entity system200. In some embodiments, the entity application 424 may be an onlinebanking application.

The memory 420 can also store any of a number of pieces of information,and data, used by the computing device system 400 and the applicationsand devices that make up the computing device system 400 or are incommunication with the computing device system 400 to implement thefunctions of the computing device system 400 and/or the other systemsdescribed herein.

FIG. 5 provides a block diagram illustrating a process flow 500 forestablishing permanent records based on micro-interactions, inaccordance with an embodiment of the invention.

As shown in block 505, the system receives a first set of interactionrequests from one or more user devices of one or more users. In someembodiments, the system may receive the first set of interactionrequests via an entity device provided by the entity associated with theentity system 200, where the entity device comprises an Near FieldCommunication (NFC) interface. In such embodiments, the first set ofinteraction requests may be NFC interaction requests. In someembodiments, the first set of interaction requests may be received viaan entity application present on the one or more user devices (e.g.,entity application 424), where the entity application provided by theentity associated with the entity system. In such embodiments, the firstset of interaction requests are NFC requests that are initiated when theone or more user devices are within proximate distance, via NFCinterfaces located on the one or more user devices. In some suchembodiments, the first set of interaction requests are initiatedautomatically when the one or more user devices are within the proximatedistance, where the one or more users associated with the one or moreuser devices have a previous interaction history. In some embodiments,the one or more users may perform the first set of the interactionrequests via the one or more user devices directly by accessing theentity application (e.g., entity application 424) or an applicationprovided by the system of the present invention (e.g., permanent recordgeneration application 421) located on the one or more user devices.

As shown in block 510, the system identifies initiation of an eventbased on receiving the first set of interaction requests from the one ormore user devices of the one or more users. The event may be anin-person event (e.g., in-person meeting). The first set of interactionrequests may be initiated at different times by the users. For example,a first user of the one or more users may initiate a first interactionrequest of the first set of interaction requests at a first time-stamp,a second user of the one or more users may initiate a second interactionrequest of the first set of interaction requests at a second time-stamp,and a third user of the one or more users may initiate a thirdinteraction request of the first set of interaction requests at a thirdtime-stamp. In some embodiments, the system records the first set oftime-stamps associated with the first set of interaction requests. Insome embodiments, the system may determine initiation of the event afterreceiving a first interaction request of the first set of interactionrequests. For example, the system may receive a first interactionrequest from a first user and may determine that the event has started.In some embodiments, the system may determine initiation of the eventreceiving at least two interaction requests of the first set ofinteraction requests. For example, the system may receive a firstinteraction request from a first user and a second interaction requestfrom a second user and may determine that the event has started.

As shown in block 515, the system initiates a first set ofmicro-interactions, wherein initiation of the first set ofmicro-interactions comprises transferring resources to one or moreresource pools associated with the one or more users. In someembodiments, the resources may be funds, digital currencies, or the likethat have monetary value. The micro-interactions may be interactionsthat involve small amount of resources (e.g., one penny, 0.00001 digitalcurrency, or the like). The one or more resource pools may be one ormore accounts (e.g., checking account, savings account, digital currencyaccounts, or the like) associated with the one or more users. In someembodiments, the system may generate unique resources for the purposesof implementing this invention. In some embodiments, the system mayperform the first set of micro-interactions via an entity application(e.g., online banking application, digital currency application)provided by the entity.

In some embodiments, the first set of micro-interactions may beinteractions between adjacent users. For example, if three users haveinitiated the 3 interaction requests, the system may initiate a firstmicro-interaction from a first resource pool of a first user to a secondresource pool of a second user, a second micro-interaction from thesecond resource pool of the second user to a third resource pool of athird user, and a third micro-interaction from the third resource poolof the third user to the first resource pool of the first user.

In some embodiments, the system may perform first micro-interaction witha first user of the one or more users and may perform the first set ofmicro-interactions excluding the first micro-interaction between a firstresource pool of a first user and resource pools of the one or moreusers excluding the first user. For example, if three users haveinitiated the 3 interaction requests, the system may transfer ‘X’ amountto a first user from an entity resource pool of the entity and maytransfer ‘Y’ amount from a first resource pool of the first user to asecond resource pool of a second user and a third resource pool of athird user. In some embodiments, the system may use total value ofresources involved with the first set of micro-interactions as a uniqueidentifier associated with the event.

As shown in block 520, the system receives a second set of interactionrequests from one or more user devices of one or more users. In someembodiments, the system may receive the second set of interactionrequests via an entity device provided by the entity associated with theentity system 200, where the entity device comprises an Near FieldCommunication (NFC) interface. In such embodiments, the second set ofinteraction requests may be NFC interaction requests. In someembodiments, the second set of interaction requests may be received viathe entity application present on the one or more user devices (e.g.,entity application 424), where the entity application provided by theentity associated with the entity system. In such embodiments, thesecond set of interaction requests are NFC requests that are initiatedwhen the one or more user devices are not within the proximate distance,via the NFC interfaces located on the one or more user devices. In somesuch embodiments, the second set of interaction requests are initiatedautomatically when the one or more user devices are not within theproximate distance. In some embodiments, the one or more users mayperform the second set of the interaction requests via the one or moreuser devices directly by accessing the entity application (e.g., entityapplication 424) or an application provided by the system of the presentinvention (e.g., permanent record generation application 421) located onthe one or more user devices.

As shown in block 525, the system identifies completion of the eventbased on receiving the second set of interaction requests from the oneor more user devices of the one or more users. The second set ofinteraction requests may be initiated at different times by the users.For example, a first user of the one or more users may initiate a firstinteraction request of the second set of interaction requests at a firsttime-stamp, a second user of the one or more users may initiate a secondinteraction request of the second set of interaction requests at asecond time-stamp, and a third user of the one or more users mayinitiate a third interaction request of the second set of interactionrequests at a third time-stamp. In some embodiments, the system recordsthe second set of time-stamps associated with the second set ofinteraction requests. In some embodiments, the system may determinecompletion of the event after receiving a last interaction request ofthe second set of interaction requests. For example, the system mayreceive a last interaction request from an n^(th) user of ‘n’ users andmay determine that the event has ended. In some embodiments, the systemmay determine last time-stamp associated with the last-interactionrequest as event completion time of the event.

As shown in block 530, the system reverts the first set ofmicro-interactions, wherein reverting the first set ofmicro-interactions comprises transferring the resources back from theone or more resource pools associated with the one or more users. Forexample, if ‘X’ amount was transferred to a first resource pool of afirst user in block 515, the system reverts the interaction of ‘X’amount.

As shown in block 535, the system creates a permanent record associatedwith the initiation of the event and the completion of the event. Thesystem may insert the first set of time-stamps and a second set oftime-stamps in the permanent record. In some embodiments, the system mayalso insert user identifiers, information associated with the first setof micro-interactions, location of the event, and any other informationassociated with the event in the permanent record. As shown in block540, the system stores the permanent record. In some embodiments, thepermanent record may be stored on a distributed register (e.g.,blockchain). In some embodiments, if the resources transferred weredigital resources, a record is automatically created on the distributedledger and the system may leverage that record and create another recordto store in a datastore.

As will be appreciated by one of skill in the art, the present inventionmay be embodied as a method (including, for example, acomputer-implemented process, a business process, and/or any otherprocess), apparatus (including, for example, a system, machine, device,computer program product, and/or the like), or a combination of theforegoing. Accordingly, embodiments of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, and thelike), or an embodiment combining software and hardware aspects that maygenerally be referred to herein as a “system.” Furthermore, embodimentsof the present invention may take the form of a computer program producton a computer-readable medium having computer-executable program codeembodied in the medium.

Any suitable transitory or non-transitory computer readable medium maybe utilized. The computer readable medium may be, for example but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device. More specific examples ofthe computer readable medium include, but are not limited to, thefollowing: an electrical connection having one or more wires; a tangiblestorage medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer readable medium may be anymedium that can contain, store, communicate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, radio frequency (RF)signals, or other mediums.

Computer-executable program code for carrying out operations ofembodiments of the present invention may be written in an objectoriented, scripted or unscripted programming language such as Java,Perl, Smalltalk, C++, or the like. However, the computer program codefor carrying out operations of embodiments of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language or similar programming languages.

Embodiments of the present invention are described above with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer-executable program codeportions. These computer-executable program code portions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the code portions, which execute via theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the code portions stored in the computer readablememory produce an article of manufacture including instructionmechanisms which implement the function/act specified in the flowchartand/or block diagram block(s).

The computer-executable program code may also be loaded onto a computeror other programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that the codeportions which execute on the computer or other programmable apparatusprovide steps for implementing the functions/acts specified in theflowchart and/or block diagram block(s). Alternatively, computer programimplemented steps or acts may be combined with operator or humanimplemented steps or acts in order to carry out an embodiment of theinvention.

As the phrase is used herein, a processor may be “configured to” performa certain function in a variety of ways, including, for example, byhaving one or more general-purpose circuits perform the function byexecuting particular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

Embodiments of the present invention are described above with referenceto flowcharts and/or block diagrams. It will be understood that steps ofthe processes described herein may be performed in orders different thanthose illustrated in the flowcharts. In other words, the processesrepresented by the blocks of a flowchart may, in some embodiments, beperformed in an order other that the order illustrated, may be combinedor divided, or may be performed simultaneously. It will also beunderstood that the blocks of the block diagrams illustrated, in someembodiments, merely conceptual delineations between systems and one ormore of the systems illustrated by a block in the block diagrams may becombined or share hardware and/or software with another one or more ofthe systems illustrated by a block in the block diagrams. Likewise, adevice, system, apparatus, and/or the like may be made up of one or moredevices, systems, apparatuses, and/or the like. For example, where aprocessor is illustrated or described herein, the processor may be madeup of a plurality of microprocessors or other processing devices whichmay or may not be coupled to one another. Likewise, where a memory isillustrated or described herein, the memory may be made up of aplurality of memory devices which may or may not be coupled to oneanother.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

What is claimed is:
 1. A system for establishing permanent records based on micro-interactions, the system comprising: a memory device with computer-readable program code stored thereon; a communication device; and a processing device operatively coupled to the memory device and the communication device, wherein the processing device is configured to execute the computer-readable program code to: identify initiation of an event based on receiving first set of interaction requests from one or more user devices of one or more users; in response to receiving the first set interaction requests, initiate a first set of micro-interactions, wherein initiation of the first set of micro-interactions comprises transferring resources to one or more resource pools associated with the one or more users; identify completion of the event based on receiving a second set of interaction requests from the one or more user devices of the one or more users; in response to receiving the second set of interaction requests, revert the first set of micro-interactions, wherein reverting the first set of micro-interactions comprises transferring the resources back from the one or more resource pools associated with the one or more users; and create a permanent record associated with the initiation of the event and the completion of the event.
 2. The system according to claim 1, wherein the processing device is further configured to execute the computer-readable program code to receive the first set of interaction requests and the second set of interaction requests from the one or more users, via an entity device comprising a Near Field Communication interface, wherein the first set of interaction requests and the second set of interaction requests are Near Field Communication interaction requests.
 3. The system according to claim 1, wherein the processing device is further configured to execute the computer-readable program code to: determine a first set of time-stamps associated with the first set of the interaction requests; and insert the first set of time-stamps in the permanent record, wherein the first set of time-stamps are associated with initiation of the event.
 4. The system according to claim 1, wherein the processing device is further configured to execute the computer-readable program code to: determine a second set of time-stamps associated with the second set of the interaction requests; and insert the second set of time-stamps in the permanent record, wherein the second set of time-stamps are associated with completion of the event.
 5. The system according to claim 4, wherein the processing device is further configured to execute the computer-readable program code to: identify completion of the event based on receiving a last interaction request of the second set of interaction request; identify a last time-stamp associated with the last interaction request; and insert the last time-stamp as event completion time-stamp in the permanent record.
 6. The system of claim 1, wherein the processing device is further configured to execute the computer-readable program code to store the permanent record on a distributed ledger.
 7. The system according to claim 1, wherein the processing device is further configured to execute the computer-readable program code to transfer the resources and revert the resources, via an entity application provided by an entity.
 8. A computer program product for establishing permanent records based on micro-interactions, the computer program product comprising at least one non-transitory computer readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions comprising executable portions for: identifying initiation of an event based on receiving first set of interaction requests from one or more user devices of one or more users; in response to receiving the first set interaction requests, initiating a first set of micro-interactions, wherein initiation of the first set of micro-interactions comprises transferring resources to one or more resource pools associated with the one or more users; identifying completion of the event based on receiving a second set of interaction requests from the one or more user devices of the one or more users; in response to receiving the second set of interaction requests, reverting the first set of micro-interactions, wherein reverting the first set of micro-interactions comprises transferring the resources back from the one or more resource pools associated with the one or more users; and creating a permanent record associated with the initiation of the event and the completion of the event.
 9. The computer program product of claim 8, wherein the computer-readable program code portions comprising executable portions for receiving the first set of interaction requests and the second set of interaction requests from the one or more users, via an entity device comprising a Near Field Communication interface, wherein the first set of interaction requests and the second set of interaction requests are Near Field Communication interaction requests.
 10. The computer program product of claim 8, wherein the computer-readable program code portions comprising executable portions for: determining a first set of time-stamps associated with the first set of the interaction requests; and inserting the first set of time-stamps in the permanent record, wherein the first set of time-stamps are associated with initiation of the event.
 11. The computer program product of claim 8, wherein the computer-readable program code portions comprising executable portions for: determining a second set of time-stamps associated with the second set of the interaction requests; and inserting the second set of time-stamps in the permanent record, wherein the second set of time-stamps are associated with completion of the event.
 12. The computer program product of claim 11, wherein the computer-readable program code portions comprising executable portions for: identifying completion of the event based on receiving a last interaction request of the second set of interaction request; identifying a last time-stamp associated with the last interaction request; and inserting the last time-stamp as event completion time-stamp in the permanent record.
 13. The computer program product of claim 8, wherein the computer-readable program code portions comprising executable portions for storing the permanent record on a distributed ledger.
 14. A computer-implemented method for establishing permanent records based on micro-interactions, the method comprising: identifying initiation of an event based on receiving first set of interaction requests from one or more user devices of one or more users; in response to receiving the first set interaction requests, initiating a first set of micro-interactions, wherein initiation of the first set of micro-interactions comprises transferring resources to one or more resource pools associated with the one or more users; identifying completion of the event based on receiving a second set of interaction requests from the one or more user devices of the one or more users; in response to receiving the second set of interaction requests, reverting the first set of micro-interactions, wherein reverting the first set of micro-interactions comprises transferring the resources back from the one or more resource pools associated with the one or more users; and creating a permanent record associated with the initiation of the event and the completion of the event.
 15. The computer-implemented method of claim 14, wherein the method further comprises receiving the first set of interaction requests and the second set of interaction requests from the one or more users, via an entity device comprising a Near Field Communication interface, wherein the first set of interaction requests and the second set of interaction requests are Near Field Communication interaction requests.
 16. The computer-implemented method of claim 14, wherein the method further comprises: determining a first set of time-stamps associated with the first set of the interaction requests; and inserting the first set of time-stamps in the permanent record, wherein the first set of time-stamps are associated with initiation of the event.
 17. The computer-implemented method of claim 14, wherein the method further comprises: determining a second set of time-stamps associated with the second set of the interaction requests; and inserting the second set of time-stamps in the permanent record, wherein the second set of time-stamps are associated with completion of the event.
 18. The computer-implemented method of claim 17, wherein the method further comprises: identifying completion of the event based on receiving a last interaction request of the second set of interaction request; identifying a last time-stamp associated with the last interaction request; and inserting the last time-stamp as event completion time-stamp in the permanent record.
 19. The computer-implemented method of claim 18, wherein the method further comprises storing the permanent record on a distributed ledger.
 20. The computer-implemented method of claim 14, wherein the method further comprises transferring the resources and revert the resources, via an entity application provided by an entity. 